Skip to content

docs(valuation): describe high/low as fair-value band bounds - #1338

Open
hogan-yuan wants to merge 1 commit into
mainfrom
docs/valuation-range-bounds
Open

hogan-yuan wants to merge 1 commit into
mainfrom
docs/valuation-range-bounds

Conversation

@hogan-yuan

Copy link
Copy Markdown
Member

Summary

  • valuations field table (en / zh-CN / zh-HK): high/low are the 5-year fair-value band's bounds, not the 5-year max/min.
  • valuation_history field table (en): same fix.
  • CLI valuation page (en / zh-CN / zh-HK): note under the example output.

Why

Found by the Longbridge AI online check (T09): the model treated low as the period minimum. For 388.HK, GET /v1/quote/valuation?indicator=pe&range=1 returns low 25.19 / high 30.05, but the 1-year series bottoms at 23.29 and tops at 32.74 (73 points below low, 70 above high). /v1/quote/valuation/detail behaves the same way (5-year low 27.3 vs series min 23.52). The upstream desc ("低于合理区间") confirms these are fair-value band bounds; the fundamental team confirmed the semantics.

Note: zh-CN / zh-HK valuation_history.mdx use a different response table without high/low, so they are left as is.

🤖 Generated with Claude Code

The valuation APIs return high/low as the upper/lower bounds of the fair-value band, not the period max/min. Fix the field tables (en/zh-CN/zh-HK) and add a note to the CLI valuation page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant